Copyright: Copyright®1994 CreatiVision Pub. Corp.


Installation Problems

Here are some of the problems commonly encountered when installing IC2:

SHARE.EXE error/Unable to open a file/Unable to add a record

You must have this line in your AUTOEXEC.BAT file:  C:\DOS\SHARE.EXE /L:500.  Where 'C:' equals your drive and '\DOS' equals your DOS directory.  Also be sure there is a space between SHARE.EXE and /L:500.  This line needs to precede any executable you may be running from the AUTOEXEC.BAT file, including Windows!  You can put it after your PATH or SET PATH statement, or after your mouse driver.

If you have any problems loading a file or adding a record to a new database, check your AUTOEXEC file to make sure SHARE.EXE has been installed and that the number of locks (the /L parameter) is 500 or more.  You should also check your CONFIG.SYS and make sure you have a minimum value of 40 for both the BUFFERS and FILES.

You will need to reboot your computer after making any of these changes.

File already exists (such as THREED.VBX, etc.)

You already have an older version of the file on your system.  Rename the other file, then run the installation program again and the files will be copied properly.  This shouldn't cause conflicts with other Visual Basic programs.

GPF's or any other problems running the program

Occasionally when files are copied to a hard disk, a file will be corrupted.  If that file happens to be a DLL, it will cause erratic problems when running the program, or you may be unable to run the program at all.  If one of your DLL's for IC2 does happen to be corrupted,  you need to delete it from your hard disk and rerun the SETUP program.  Here are two of the more important DLL's for IC2 which may cause problems if they are corrupt.  They can be found in the \WINDOWS\SYSTEM directory:

VBRUN300.DLL

MSAJT110.DLL

If you experience unusual problems when running or attempting to run IC2, try deleting these two files and re-running the SETUP program.  Contact CreatiVision Publishing if you continue to experience erratic performance, or are unable to get IC2 to run at all.